App Management

An object, through which applications definitions stored in-memory can be programmatically imported or removed.

The instance of the application.

Application caption.

Application icon.

Instances of that app.

Application name.

Application title.

Generic object for passing properties, settings, etc., in the for of key/value pairs.

Application version.

Name of the Channel which the window will join.

Window height.

Distance of the top left window corner from the left edge of the screen.

Direction ("bottom", "top", "left", "right") of positioning the window relatively to the relativeTo window. Considered only if relativeTo is supplied.

The ID of the window that will be used to relatively position the new window. Can be combined with relativeDirection.

Distance of the top left window corner from the top edge of the screen.

Window width.

If true, the Channel Selector will be enabled for the window.

Application caption.

Generic object for passing properties, settings, etc., in the for of key/value pairs. Accessed using the app.userProperties property.

Detailed configuration.

The FDC3 2.0 version of the definition. If set, this means the current definition was imported as FDC3 2.0 and parsed to IOConnectBrowser one.

If set to true, the application will not be listed in the io.Connect Browser Launchpad. Defaults to false.

Application icon.

The list of intents implemented by the Application

Application name. Should be unique.

The title of the app. Sets the window's title.

Type of the application - the only supported type in io.Connect Browser is "window". More complex types are available in io.Connect Desktop.

Application version.

Settings for the Channel Selector displayed on an io.Connect Window.

Window height.

Configuration for the sandbox attribute of the <iframe> element in which the app will be started when opened in a Workspace.

Distance of the top left window corner from the left edge of the screen.

Distance of the top left window corner from the top edge of the screen.

Window width.

Configuration for the sandbox attribute of the <iframe> element in which the app will be started when opened in a Workspace.

The unique application identifier located within a specific application directory instance.

Optional e - mail to receive queries about the application.

An optional set of name value pairs that can be used to deliver custom data from an App Directory to a launcher.

Description of the application.This will typically be a 1 - 2 paragraph style blurb about the application.Allow mark up language.

Holds Icons used for the application, a Launcher may be able to use multiple Icon sizes or there may be a 'button' Icon.

Array of images to show the user when they are looking at app description.Each image can have an optional description / tooltip.

The list of intents implemented by the Application

URI or full JSON of the application manifest providing all details related to launch and use requirements as described by the vendor. The format of this manifest is vendor specific, but can be identified by the manifestType attribute.

The manifest type which relates to the format and structure of the manifest content. The definition is based on the vendor specific format and definition outside of this specification.

Application name. Should be unique.

The name of the company that owns the application.The publisher has control over their namespace / app / signature.

Optional e - mail to receive support requests for the application.

The title of the application. Sets the window's title.

Optional tooltip description e.g. for a launcher.

Application version.

The unique application identifier located within a specific application directory instance.

An array of string categories that describe the application. These are meant as a hint to catalogs or stores listing FDC3-enabled apps and it is expected that these will make a best effort to find appropriate categories (or category) under which to list the app.

Optional e-mail to receive queries about the application

An optional set of name value pairs that can be used to deliver custom data from an App Directory to a launcher

Description of the application. This will typically be a 1-2 paragraph style blurb about the application.

The type specific launch details of the application. These details are intended to be vendor-agnostic and MAY be duplicated or overridden by details provided in the hostManifests object for a specific host.

A mapping from host name to a host-specific application manifest object or URI from which that manifest can be retrieved. The manifest should provide details required to launch and use the application within the specified host. The manifest MAY duplicate or override information provided in the details field.

Holds Icons used for the application, a Launcher may be able to use multiple Icon sizes or there may be a 'button' Icon

Metadata that describes how the application uses FDC3 APIs. This metadata serves multiple purposes:

• It supports intent resolution by a desktop agent, by declaring what intents an app listens for.
• It may be used, for example in an app catalog UI, to find apps that 'interoperate with' other apps.\
• It provides a standard location to document how the app interacts with user channels, app channels, and intents, for use by other app developers and desktop assemblers.

A language tag that specifies the primary language of both the application and its AppD entry, as defined by IETF RFC 5646.

Provides localized alternatives to any field of the AppD record, which may also refer to an alternative version of the application that is also localized (e.g. by providing an alternative URL). The keys to this object should be language tags as defined by IETF RFC 5646, e.g. en, en-GB or fr-FR.

Optional URL that provides more information about the application

The name of the application. The name should be unique within an FDC3 App Directory instance. The exception to the uniqueness constraint is that an App Directory can hold definitions for multiple versions of the same app. The same appName could occur in other directories. We are not currently specifying app name conventions in the document.

The name of the company that owns the application. The publisher has control over their namespace/app/signature.

Array of images to show the user when they are looking at app description. Each image can have an optional description/tooltip

Optional e-mail to receive support requests for the application

Optional title for the application, if missing use appName, typically used in a launcher UI.

Optional tooltip description e.g. for a launcher

Enum: "web" "native" "citrix" "onlineNative" "other". The technology type that is used to launch and run the application. Each application type implies a particular set of launch details

Version of the application. This allows multiple app versions to be defined using the same app name. This can be a triplet but can also include things like 1.2.5 (BETA)

Icon URL.

Collection of flags that will be applied to the <iframe> element when the app is opened in a Workspace.

App Image URL.

A list of application names and errors of all the unsuccessful imports

A list of names of the successfully imported application definitions

Interop instance. Use this to invoke Interop methods for that instance.

Instance ID.

A comma separated list of the types of contexts the intent offered by the application can process, here the first part of the context type is the namespace e.g."fdc3.contact, org.symphony.contact".

Custom configuration for the intent that may be required for a particular desktop agent.

An optional display name for the intent that may be used in UI instead of the name.

The name of the intent to 'launch'. In this case the name of an Intent supported by an Application.

Result type may be a type name, the string "channel" (which indicates that the app will return a channel) or a string indicating a channel that returns a specific type, e.g. "channel<fdc3.instrument>"

Collection of flags that will be applied to the <iframe> element when the app is opened in a Workspace.